Walkthrough

GithubDispatcher is refactored to use a new store abstraction instead of a repository-based store. A GithubEntities handler is introduced in the store package. Workspace initialization logic now persists GitHub entities. Related test infrastructure and dispatcher call sites are updated accordingly.

Changes

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

The changes involve a consistent refactoring pattern (dependency injection swap from repository to store) applied across multiple files, but require verification that all call sites transition correctly. The new GithubEntities handler introduces straightforward CRUD-like operations. Mix of structural changes and test updates across six files across multiple packages demands careful attention to ensure the old getGithubEntity logic is properly replicated in the new store abstraction.

Possibly related PRs

• chore: gh job dispatch go #680: Introduced the repository-based GithubDispatcher implementation that this PR refactors to use the new store abstraction.

Suggested reviewers

• jsbroks

Poem

🐰 From repos to stores, the dispatcher takes flight,
GitHub entities now nestled in storage so bright,
With Upsert and Get, the refactoring's right,
One abstraction to bind them—what elegant might! ✨

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}